Location for unmanned aerial vehicle landing and taking off

ABSTRACT

A UAV location management method for use with a flight management system is provided, where the method comprises providing a location for at least one unmanned aerial vehicle (UAV) for at least one of: landing, taking-off and loading, providing at least a first weight-sensitive UAV pad at the UAV location, assigning a gross weight limit to each UAV scheduled to take-off from the first weight-sensitive UAV pad, the gross weight limit being based on a safety factor and at least one of: (i) a characteristic of the UAV; (ii) a characteristic of a power source of the UAV; (iii) a scheduled flight path for the UAV; and (iv) a weather condition, monitoring a weight exerted on the first weight-sensitive UAV pad when the UAV is positioned on the UAV pad, and transmitting a halt-flight signal to the flight management system for the UAV where the weight exceeds the gross weight limit.

RELATED APPLICATION

This application is a Continuation of application Ser. No. 16/851,685filed Apr. 17, 2020, which is a Continuation-in-Part of application Ser.No. 15/299,923 filed Oct. 21, 2016, which claims the benefit of U.S.Provisional Application No. 62/355,024, filed on Jun. 27, 2016, theentire content of these applications is herein incorporated byreference.

FIELD

The present disclosure relates to unmanned aerial vehicles, andlocations or facilities for unmanned vehicles.

INTRODUCTION

The following paragraphs are not an admission that anything discussed inthem is prior art or part of the knowledge of persons skilled in theart.

Unmanned aerial vehicles (UAVs) have been coming into prominence andhave been implemented in limited situations. One obstacle to expandingthe uses of UAVs may be public safety. UAVs have also been proposed fordelivering of articles, but there is no practical proposal for deliveryof articles for customers or users who have little knowledge orfamiliarity with UAVs.

Know proposals for using UAVs can be found in U.S. Pat. Nos. 9,174,733and 9,244,147; and U.S. Publication Nos. 201201453482, 20140032034 and20150120094, the contents of all of which are incorporated by reference.

SUMMARY

The following is intended to introduce the reader to the detaileddescription that follows and not to define or limit the claimed subjectmatter.

In accordance with a first aspect of the disclosure, there is providedan unmanned aerial vehicle (UAV) system for operation with a flightmanagement system, comprising:

a plurality of controlled access UAV zones, each being for at least oneof: UAV landing, UAV loading, and UAV take-off, that is accessible by aUAV;

a control and communication unit for controlling access to each UAVzone;

for each zone, a barrier around the zone to enclose that zone and tocontrol entry into that zone by users, an opening in the barrier topermit personnel to enter into that zone, a closure for the opening, andat least one remotely operable lock for the closure; and

for each zone, a communications module operable to control the lock forthat zone to govern access to and entry into that zone by users;

a flight management system separate from the plurality of zones and incommunication with the control and communication unit and with eachcommunications module, and responsive to requests by users to allowaccess to a selected UAV zone by opening the lock associated with theclosure for that UAV zone; and

at least some of the UAV zones are charging zones that include at leastone charging cable for charging a battery of a UAV.

The unmanned aerial vehicle (UAV) system may include a control andcommunication unit for each UAV zone, providing control of the lock forthe closure for that UAV zone and in communication with the flightmanagement system.

Each charging zone and the control and communication unit therefor maybe controlled by the flight management system, to control and to monitorcharging of a UAV.

Each charging zone may include at least one charging cable for chargingand avionics battery of a UAV and another charging cable for charging apropulsion battery of a UAV, and each charging cable may include aconnector for connecting to a UAV.

The charging cables may be provided with connectors enabling automaticconnection to a UAV without manual input.

For each charging zone, the control and communication unit therefor maybe adapted to receive data from a UAV indicating charging parameters forthe batteries of the UAV, optionally including current and voltage.

The unmanned aerial vehicle (UAV) system may include at least one UAVzone provided with at least medical supplies for transportation by UAV,each UAV zone with medical supplies comprising a medical supplylocation.

Each medical supply location may include a connection between the flightmanagement system and the medical supplies, for monitoring the status ofthe medical supplies.

Each medical supply location may include a UAV, with the medicalsupplies attached to the UAV, for transportation and delivery of themedical supplies.

Each medical supply location may include at least one charging cableconnected to the UAV, for maintaining UAV batteries in a chargedcondition, and wherein the flight management system is in communicationwith the UAV to monitor the charge state of the UAV.

A connection between said at least one charging cable and the UAV, maypermit the UAV to disengage from the charging cable and apart from themedical supply location, without manual intervention.

The unmanned aerial vehicle (UAV) system may include a housing with aclosure, housing and protecting the UAV and the medical supplies, theclosure being openable by the flight management system, to permit theUAV with the medical supplies to depart from the medical supplylocation.

The medical supply locations may be selected and spaced within the UAVzones, to ensure that all points within a selected geographic area canbe reached by a UAV with medical supplies from at least one of themedical supply locations. At least some of the medical supply locationsmay be provided at one of a hospital, doctors' offices and other medicalfacilities.

Another aspect of the present disclosure provides a method of managing aplurality of unmanned aerial vehicle (UAV) landing and take-offlocations, at least some of the locations being spaced apart whereby onelocation can serve as a departure location and another location canserve as a destination location, the method comprising the steps of:

providing, for each location, an enclosure defined by a barrier topersonnel, the enclosure including at least one zone for landing andtake-off of a UAV and accessible by a UAV;

providing, for each location, an opening in the barrier to permitpersonnel to enter the enclosure and a closure for closing the opening;

providing, for each location, a remotely actuatable lock for theclosure; and

actuating the lock for each location, to permit opening of the closurethereof, thereby to enable users to enter that enclosure.

The method may include providing, for each location, a control andcommunications unit a connected to the lock for that location, andrequiring a user to input an access code to the control andcommunications unit for that location to open that lock.

The method may include enabling a user to enter an access code through auser electronic device.

The method may include providing an input device on the exterior of thelocation, requiring a user to input at least one of a username and apassword to the input device, and further providing for user toacknowledge a communication to a user electronic device, to provide fortwo factor authentication.

The method may include providing for different levels of access,including controlling access to each location with a flight managementsystem, only enabling access to public users when the flight managementsystem determines that the location is clear and unobstructed and theuser has the right to access a UAV at that location.

The method may include providing access to operators of a location, toenable maintenance and cleanup of any obstructions

The method may include providing differential charging for access to thelocation, the differential charging including at least one of: chargingdifferent amounts for access at different times; varying chargesdepending upon the demand for access to the location; and providingdifferent charging for exclusive access to a location.

The method may include providing at least one location with medicalsupplies, for delivery by a UAV, as a medical supply location andpermitting access to each medical supply location only to selected,medically qualified users.

The method may include providing a UAV at each medical supply location,providing the charging of that UAV, monitoring the state of charge ofthe UAV, and only deploying the UAV with the medical supplies when theUAV is adequately charged.

The method may include providing charging for UAVs at a location,monitoring the charge of a UAV is location, and charging for thecharging services.

BRIEF DESCRIPTION OF THE FIGURES

For a better understanding of the described embodiments and to show moreclearly how they may be carried into effect, reference will now be made,by way of example, to the accompanying drawings in which:

FIG. 1 is a schematic of an example location for unmanned aerial vehicle(UAV) landing and taking off, according to one embodiment;

FIGS. 2 and 3 are schematic examples of other embodiments of a locationfor UAV landing and taking off;

FIG. 4 is a schematic side section view of an example UAV pad, accordingto one embodiment;

FIG. 5 is a schematic of an example location for unmanned aerial vehicle(UAV) landing and taking off, according to a further embodiment,including provision for charging UAVs and storage of medical suppliesand/or a UAV for delivery of the medical supplies;

FIG. 6 is a schematic perspective view of a control and communicationunit providing various functions for UAVs; and

FIG. 7 shows schematic examples of other embodiments of a location forUAV landing and taking off.

DETAILED DESCRIPTION

Various systems, apparatuses or methods will be described below toprovide an example of an embodiment of each claimed invention. Noembodiment described below limits any claimed invention and any claimedinvention may cover apparatuses and methods that differ from thosedescribed below. The claimed inventions are not limited to systems,apparatuses and methods having all of the features of any one apparatusor method described below, or to features common to multiple or all ofthe systems, apparatuses or methods described below. It is possible thata system, apparatus or method described below is not an embodiment ofany claimed invention. Any invention disclosed in a system, apparatus ormethod described below that is not claimed in this document may be thesubject matter of another protective instrument, for example, acontinuing patent application, and the applicant(s), inventor(s) and/orowner(s) do not intend to abandon, disclaim or dedicate to the publicany such invention by its disclosure in this document.

Various embodiments of a location 100 for unmanned aerial vehicle (UAV)102 landing and taking off are described below.

Reference is now made to FIG. 1, which shows an example location for aUAV 102 landing and taking off. The location 100 has an enclosure 106, abarrier 104 around the enclosure 106, at least one of a landing zone108, 126 and a take-off zone 108, 126 in the enclosure 106, an opening110 in the barrier 104, a closure 112 for the opening 110, a controlpanel 116, a flight management system 150, and at least one remotelyoperable lock 114 for the enclosure 106. The control panel 116 may beoperable to provide for restricting access and granting access to thelocation 100. As shown, the lock 114 may be connected to at least one ofthe control panel 116 and the flight management system 150, e.g.wirelessly. In one example, the closure 112 may be provided as a gate112 operable to selectively provide and restrict ground access to thelocation 100 via the opening 110.

While a control panel 116 is shown separately from the lock 114, theycould be combined in one device. Where there are a plurality of locks,each could have the necessary functionality of the control panel tocommunicate with the flight management system, or one lock could be a‘master lock’ with this functionality, and other locks could be ‘slavelocks’ controlled by the master lock. In this case, a separatecommunication device(s) can be provided for communications with user,which can include a touchscreen, visual indication of status of locks,etc.

Each of the zones 108, 126 may be identified as being for only one oflanding and taking off, or may be designated for both landing and takingoff. For a zone designated or used only for taking off an identifier maynot be so critical, but is preferred as it enables the UAV to read theidentifier and ensure it is departing from the correct location.

The barrier 104 and the gate or closure 112 can be provided in the formof a wire mesh fence with a gate also formed of wire mesh on a frame,for example. The height of the barrier 104 and fence 112 can be in therange of 6 to 8 feet (or approx. 1.85 to 2.45 metres). The barrier mayalternatively be in the form of a wall. Additionally, while the location100 is shown with a vertical enclosure open at the top, for UAVs toenter and exit vertically, other configurations are possible,particularly for winged UAVs that require horizontal landing andtake-off facilities. The location 100 could be provided with a coveringor roof partially or completely covering the location 100. At least fora full cover over the location 100, part of the cover will be movable toopen the location to access by UAVs. The use of a cover or roof may haveadvantages in climates subject to snow or other precipitation harmful toUAVs. Further, as even rotor powered UAVs can land and take-offessentially horizontally, the location 100 may have a complete and fixedroof or cover, with the UAVs entering and leaving the zone from oneside. (Although, for rotor driven UAVs, the immediate motion on arrivingand leaving a landing or take-off zone may be vertical, this need onlybe for a small distance.) In this case an open side may include doors orgates to close off the location 100. This may particularly applicable,when the location can be provided on top of a building. In this case theopen side of the location 100 may be provided continuous with a sidewall of the building, so that even when open, it does not provide anaccess opening to unauthorized personnel.

In one aspect, the control panel 116 may be operable to store an accesscode for the location 100, and to receive updates to the access codefrom the flight management system 150. In another aspect, the controlpanel 116 may be operable to store additional access codes for thelocation 100. For example, additional access codes may be programmableinto the control panel 116 via at least one of an input-output deviceconnected to the control panel 116 The control panel may be configuredfor communication with user handheld or mobile devices, such assmartphones and tablet computers, and for this purpose user handhelddevices may have a mobile app adapted to communicate with the controlpanel 116 and/or the lock 114. The control panel 116 may provide thesame functions as the control and communications unit described below.

At least one of the control panel 116 and the flight management system150 may be operable to assign various access levels to the additionalaccess codes. In some examples, the access levels may includerestrictions on access times, times of day during which a given code maybe used, and locations 100 to which the codes may grant access. In otherexamples, the access levels may also include one or more safetyinterlocks with various conditions for a given location 100. Forexample, a particular access code may be programmed to provide groundaccess to the location 100 irrespective of whether a condition (such as,for example, an obstruction) at the location 100, which condition maysuspend other access codes, exists. Such an access code would beassigned to a person in a supervisory role, responsible for themaintenance of the location 100.

In another aspect, the location 100 may include a first sensor operableto detect an obstruction within the location. The control panel 116 maybe operable to restrict access to the location upon detection of anobstruction to the location by the first sensor. In one example, thefirst sensor may include a video sensor 120 or a video surveillanceapparatus 120. In another example, the first sensor may include a videosensor 120 operable with at least one processor executing instructionsstored on a non-transitory memory to detect an obstruction. In yet otherexamples, the location 100 may include a second sensor operable with thefirst sensor to detect an obstruction. In one example, the second sensormay include an infrared sensor. In a particular example, the firstsensor may be operable to detect a quantity of obstructions, and thesecond sensor may be operable to detect, for each obstruction, a type ofthe obstruction. Other possible sensors are thermal sensors andphoto-electric sensors, where interruption of a laser beam on light beamindicates the presence of an unwanted object.

In some embodiments, the first sensor may be operable with at least oneprocessor to detect at least one of an animate object and an inanimateobject. In some embodiments, the first sensor may be operable with thesecond sensor to detect at least one of an animate object and aninanimate object. Such objects may be obstructions to the location 100in that they may pose a risk to UAV 102 landings and take-offs,depending on the nature of the object(s). The control panel 116 may beoperable with the flight management system 150 to halt all UAV landingsand take-offs to and from the location 100 upon the detection of anobstruction. Examples of inanimate objects that may be obstructions mayinclude: leaves, tree branches, and articles of garbage which may be,for example, blown into a given location 100 by a wind. Examples ofanimate objects that may be obstructions may include: persons andanimals.

In one example, the control panel 116 may be operable to determine theobstruction to be one of: at least one animate object, at least oneinanimate object, and at least one animate object in combination with atleast one inanimate object. In other examples, at least one of thecontrol panel 116 and the flight management system 150 may be operableto perform the determination. For example, the control panel 116 may beoperable with the first sensor to distinguish between animate andinanimate projects, and in at least some embodiments to also distinguishwhether the one type, the other type, or both types of objects arepresent within the location 100.

Obstructions such as animate and inanimate objects may pose a risk toUAV 102 landings and take-offs. UAV 102 landings and take-offs may posea risk, such as a risk of injury or death, to the animate objects. Insome examples, animate objects may be removed from the location 100 byproviding, for example, at least one of an audio 124 and a visual 122signal to the animate objects. In one example, a given color of lightsignal may be provided along with, for example, a buzzer. In oneexample, the light signal may be provided by at least one light source122. The at least one light source 122 may be mounted on, for example,the enclosure 106. In other examples, a siren 124 may be provided togenerate a sound at the location 100. In an aspect, a siren 124 may beoperable to scare off animals from the location 100.

To discourage animals, and insects from entering or staying in thelocation, the location can be provided with a high frequency soundsource, at a frequency that is inaudible to humans. This can be runcontinuously, or before and during a UAV take-off and landing, asrequired.

In some embodiments, the location 100 may include a cleaner 118 operableto remove at least inanimate objects from the location 100. Depending onthe embodiment of the cleaner 118 selected for a particular embodimentof the location 100, it may be safe to operate the cleaner 118 even whenan animate object is present within the location 100. One such examplecleaner 118 may include an automated vacuum robot movable within thelocation 100 and equipped with collision and location sensors operableto allow the robot to avoid collisions and to operate within thelocation 100. In some cases, the cleaner 118 may be programmable tooperate in designated parts of the location 100.

The parts may be designated by, for example, at least one combination ofan infrared light source and a corresponding infrared sensor. Theinfrared light and sensor combination may be operable with at least thecontrol panel to detect when the cleaner 118 interrupts a line of“sight” between the source and sensor, and in response send a signal tothe cleaner 118 to change at least one operating characteristic of thecleaner 118. In one example, the characteristic may include a directionof motion of the cleaner 118.

A suitable cleaner 118 may be selected based on a given embodiment ofthe location 100. The cleaner 118 may be selected to be suitable forremoving the types of obstructions that may be expected to occur at thegiven location 100. In one example, the cleaner 118 may be an air blower118 disposed within the location 100. The blower 118 may be operable togenerate and direct an air stream to the location 100 to remove at leastone type of obstruction from the location 100.

Depending on the features of a given embodiment of the location 100 andthe at least one UAV 102 used with the location 100, operating thecleaner 118 may pose a risk to at least one of the at least one UAV 102and animate objects that may be present within the location 100 atvarious times. In other examples, operating the cleaner 118 may causediscomfort to the animate objects. Accordingly, the control panel 116may be operable to start the cleaner 118 when the location 100 is freefrom UAV 102 landings and take-offs and the obstruction is determined tobe at least one inanimate object

In another aspect, the control panel 116 may be operable to: a) provideat least one warning signal, such as for example described above, whenat least one animate obstruction and at least one inanimate obstructionis detected; b) monitor the animate obstruction; and c) start thecleaner 118 after the control panel receives an indication (for example,a signal) that the location 100 is free from animate obstructions andcontains at least one inanimate obstruction. In yet other examples, thecontrol panel 116 may be operable to generate a signal to halt all UAVlandings and take-offs scheduled for the location 100, then start thecleaner 118, and then generate a signal to resume UAV landings andtake-offs once it is determined that the location 100 is free fromobstructions.

Depending on the use of a given embodiment of the location 100, it maybe desirable to record at least one form of proof of UAV 102 landingsand take-offs. In more particular examples, it may be desirable torecord at least one form of proof of safe UAV 102 landings andtake-offs. In some examples, the location 100 may include at least onesensor operable with at least one of a computing system and a processorto detect at least one of an approach, landing, and take-off of the atleast one UAV 102 and to record a video of the at least one approach,landing, and take-off.

A UAV location management method for use with a flight management systemis described next. In another aspect, a method of managing an unmannedaerial vehicle (UAV) landing and take-off location is also described.

The method may include providing a location 100 for at least one of UAV102 landing and taking off, providing a cleaner 118 for the location100, and by using at least one computing system: a) monitoring for atleast one obstruction to the location 100; and b) determining the atleast one obstruction as being one of: at least one animate object, atleast one inanimate object, and at least one animate object incombination with at least one inanimate object.

The method may further include, when the obstruction is determined to beat least one inanimate object, performing at least one of: a)restricting access to the location 100; b) transmitting an instructionto the flight management system 150 to halt UAV 102 flights andtake-offs to and from the location 100; and c) transmitting aninstruction to the cleaner 118 to remove the inanimate object from thelocation 100.

In another aspect, the method may also include providing at least one ofan audible 124 and a visual 122 notification at the location 100 when anobstruction is detected. In another aspect, the method may also includeproviding at least one of an audio 122 and visual 124 notification ofeach UAV 102 landing and take-off.

Additionally both before and during landing and take-off, the audibleand visual notification devices 122, 124 can be operated to deteranimals, etc. Also, as a standard part of any UAV landing or take-off,blowers and other cleaning devices can be operate before the landing ortake-off.

In another aspect, the method, as shown in FIG. 4, may also include:providing at least a first weight-sensitive UAV pad 200 for each of thezones 108, 126 for at least UAV 102 take-offs; and by using at least onecomputing system: 1) assigning a gross weight limit to each UAV 102scheduled to take-off from the UAV pad 200, the limit being based on asafety factor and at least one of: a) a characteristic of the UAV 102,b) a characteristic of a power source of the UAV 102, c) a scheduledflight path for the UAV 102, d) and a weather condition; 2) monitoring aweight exerted on the UAV pad 200 when the UAV 102 is positioned on theUAV pad 200; and 3) transmitting a halt-flight signal to the flightmanagement system 150 for the UAV 102 where the weight exceeds thelimit.

The location 100 can also include a computer portal or monitor 132and/or a display 140. The monitor 132 can include an input keyboard anddisplay 136, which can be combined as a touchscreen. It can additionallyinclude a printer 138, for printing various documents. For example, theprinter could be used to print a label for adhering to an article to bedelivered, with the label bearing a barcode or other machine-readablecode. The code can then be scanned or read at various locations, totrack delivery of an article. Various electrically powered devices atthe location 100, including the monitor 132 can be connected to aconventional electrical supply and/or to a solar panel 134. Where thesolar panel is provided, backup battery capacity can be provided.

Reference is now briefly made to FIG. 4. In a particular example, theweight-sensitive UAV pad 200 may comprise a pad body 204 and a level pad202 slidable up 208 and down 208 relative to the body 204. The body 204may include at least one weight sensor 210 in communication with atleast one of the control panel 116 (FIG. 1) and a processor. The levelpad 202 may be sized to accommodate for at least one of a landing and atake-off of the at least one UAV 102.

In yet another aspect, the method may also include providing a firstUAV-readable identifier 128 for the first UAV pad 200, the identifier128 identifying at least one of: a location 100 of the UAV pad 200, andan identity of the UAV pad 200. In yet another aspect, the method mayalso include providing at least a second UAV pad 200 for at least UAV102 take-offs, and providing a second UAV-readable identifier 130 forthe second UAV pad 200. In some examples, the second identifier 130 maybe UAV-distinguishable from the first identifier 128. More than two UAVzones, for landing and taking off, can be provided, as required.

Each identifier optionally can include a logo, trademark or otherindicia indicative of an operator of the system. Alternatively or aswell, each identifier could include a logo, trademark or other indiciaof a person, business or organization associated with or managing aparticular location. Thus, if a location is provided at a business orshopping mall, that business or shopping mall may want to incorporatetheir name, logo, etc. into the identifier 128, 130.

In some examples, at least one of the identifiers 128, 130 may includeat least one mark that may be distinguishable, and in some casesreadable, by a UAV 102. For example, a UAV 102 may include a sensoroperable with a processor to distinguish, and in some cases read, themark. In a particular example, the mark may include a matrix barcode128, 130, such as a Quick Response Code™. In a particular example, theUAV 102 may include a video sensor in communication with a processor,and the video sensor may be operable with the processor to captureimages of the ground in a vicinity of the UAV 102 and monitor the imagesfor the presence of the mark. Upon detecting the mark, the processor mayinterpret, for example, particular geometrical features of the mark togenerate information pertaining to the mark and UAV zone 108, 126. Insome cases, the processor may execute instructions stored on anon-transient memory in order to refine the images using, for example,Reed-Solomon error correction, until the processor can interpret theimages. The identifiers 128, 130 may also include beacons that transmita signal that can be identified by a UAV and used to home in on thedesired UAV zone 108, 126.

In another aspect, the method may also include, by using at least onecomputing system: providing a video feed showing the location 100; andat least when an obstruction in the location 100 is detected, renderingthe feed available on at least one channel to be accessed by at leastone of: a) an operator of the flight management system 150, and b) anoperator of the location 100. The method may further include providingat least one channel for receiving, from at least one of the operators,an override to at least one of the steps of: a) restricting access tothe location 100, and b) transmitting an instruction to the flightmanagement system 150 to halt all UAV 102 flights and take-offs to andfrom the location 100.

In yet another aspect, the method may also include, by using at leastone computing system: controlling ground access to the location 100 byrequiring a user to enter a ground access code, upon receiving a requestfrom the user for ground access; having the flight management system 150send the user an access code, that many be sent to a user handhelddevice; having the user enter the access code at the control panel 116;denying the ground access where the ground access code is incorrect; andgranting the ground access when the correct access code is entered.

In examples where the location 100 includes an opening 110 and a gate112 for the opening being selectively lockable and unlockable via a lock114, the granting of ground access may include unlocking the lock 114and denying the ground access may include locking the lock 114.

In yet another aspect, the method may also include providing at leastone of an internet connection, a cellular connection, a satelliteconnection, a private RF connection, a wired connection and a wirelessconnection for the flight management system 150 to access the at leastone channel and communicate with the control panel 116. The flightmanagement system 150 may be operable to control the at least one UAV102 during at least one of: take-off from and landing to a givenembodiment of the location 100, and in transit operation. In someexamples, the control panel 116 may be operable with the flightmanagement system 150 to control the at least one UAV 102 during atleast one of: take-off from and landing to the location 100. In yetother examples, the control panel 116 may be operable to provide back-upcontrol of the at least one UAV 102 in the case of failure of the flightmanagement system 150.

For example, the control panel 116 may be operable to receive flightmanagement system 150 status updates from the flight management system150 at pre-programmed intervals. The control panel 116 may be operableto transmit a control-takeover signal to the at least one UAV 102 inresponse to receiving no (i.e. failing to receive) status updates fromthe flight management system 150 during a pre-set period of time. Inother examples, the control panel 116 may be operable with the flightmanagement system 150 to track the status of the at least one UAV as atleast one of: scheduled to land, landing, scheduled to take-off, takingoff, and in transit. The control panel 116 may be configured to becapable of sending the control-takeover signal when the status of the atleast one UAV is one of: scheduled to land, landing, scheduled totake-off, and taking off.

Additionally, the method may comprise the following steps, at adeparture location 100, selected for a requested delivery:

(i) after receiving a request for delivery of an article, at either thecontrol panel 116 or the flight management system 150, generating adeparture access code for a location 100 that is a departure locationfor the requested delivery;

(ii) transmitting the access code to one or more persons associated withthe delivery request, who are senders of the article (as part of thedelivery request or order, a customer may be asked for contactinformation for one or more senders at the departure location and one ormore receivers at the destination location, for transmission of accesscodes);

(iii) the access codes may be transmitted wirelessly or otherwise, toeach senders portable device such as a smart phone, tablet computer andthe like and to the control panel 116 at the departure location;

(iv) a sender with the access code will approach the departure location100, but will not be permitted access until a UAV selected for thedelivery is present at the departure location 100; in some cases arequired UAV may already be present and waiting, while in others therewill be some delay until a UAV can be sent and arrives from some otherlocation;

(v) once the UAV 102 is present at the departure location 100 (andoptionally in the case of a recently arrived UAV, after providing timefor rotors to come to rest), the flight management system 150 checks thedeparture location 100 using available sensors and/or visually checkingthe location using the surveillance apparatus 120, which may be doneeither by a computer generated check for unauthorized movement orpresence of unauthorized objects, or by an operator examining images ofthe departure location 100; once it is confirmed that there are noobstructions at the departure location 100, the flight management system150 will transmit to the control panel 116 a signal permitting the lock114 to be opened; optionally, a visual indication can be provided by thecontrol panel 116, e.g. on a screen and/or a signal sent to each senderhaving the access code for the departure location 100 that the locationis now available for access;

(vi) a sender can then enter the departure access code, which may beeither by way of a keypad at the departure location 100 or bytransmitting the access code using suitable short range wirelesstransmission from a handheld device, such as Bluetooth™, whichnecessarily will require an individual to be present;

(vii) on receipt of the access code, the control panel 116 will open thelock 114, and the sender can then enter the departure location 100;

(viii) as required, the printer 138 can be used as detailed above toprint a label for an article to be delivered and the sender will thenattach the label to the article;

(ix) the sender will then approach the UAV and secure the article to theUAV as a payload for delivery; this may comprise the sender opening acompartment in the UAV placing the article in the compartment andclosing the compartment, e.g. by an unlatching an latching operation;the UAV will have sensors to detect opening and closing of the articlecompartment, which will be transmitted to the control panel 116 and tothe flight management system 150;

(x) the sender may be required to carry out a series of checks andindicate that each of these has been carried out, e.g. by checking boxesin a list or a screen of the control panel 116 or on a user's handhelddevice; these checks can include: is area clear; has a visual inspectionbeen completed; is UAV intact and undamaged including check that allrotors are present, secured and with no obvious damage;

(xi) the sender will then exit the departure location, which may requirereentering of the departure access code to open the gate 112; optionallyif the sender does not exit within a prescribed time period, acommunication can be sent to the sender's handheld device to remindhim/her to exit;

(xii) as earlier, sensors at the departure location 100 including thevideo sensor or surveillance apparatus 120 may then be used to confirmthat the sender has exited the location 100; the lock 114 will then beclosed and will not permit the sender to reopen the lock 114, even ifthe access code is entered again;

(xiii) the flight management system 150 may then run required pre-flightchecks on the UAV 102 including, for example, checking the weight of theUAV with the article, checking on the available battery life for theUAV, and a final check on weather along the route for the delivery; and

(xiv) if the checks are all clear, the UAV will then be instructed bythe flight management system 150 to commence the delivery; at this time,optionally, a communication can be sent to all parties involved in thedelivery (again as detailed by the person requesting delivery) that thedelivery has commenced, which will usually include a sender at thedeparture location and a receiver at the destination location, and thismay include an anticipated arrival time.

Correspondingly, at a destination location 100 (it will be understoodthat the departure and destination locations will be separate, but thesame reference numeral is used for both, as both of them will havesimilar elements as shown in the Figures and as described), the methodcan include the flight management system generating a destination accesscode that will be transmitted to the person requesting the delivery, andwhich may be the same as or different from the departure access code.The method at the destination location can include the followingadditional steps:

(i) as detailed elsewhere, the UAV 102 will be permitted to land at thelocation, once it is confirmed that the closure 112 is closed and lockedand that there are no obstructions present; as for the departuresequence, a receiver may be required to enter the location and toperform and to confirm visual checks;

(ii) as for the departure sequence, a destination access code will besent to each receiver that has been identified to the flight managementsystem 150 and to the control panel 116 at the destination location;

(iii) after the UAV 102 has landed at the destination location 100 and,optionally, after allowing a suitable period of time for the rotors ofthe UAV to come to rest, the control panel 116 and/or the flightmanagement system 150 will send a signal to the lock 114, to permit itto be opened by the destination access code;

(iv) the receiver will then enter the destination access code at thedestination location 100; as for the departure location, this may bedone either by entering the access code on a local keypad, or by way ofshort range wireless communication, e.g. Bluetooth™, from a handhelddevice or the like;

(v) with the destination access code entered, the lock 114 is opened,and the receiver may open the gate or closure 112, to gain access to thedestination location 100;

(vi) optionally, to ensure all necessary actions are completed, the lock114 may then be closed, and may only be opened once the receiver hascompleted required actions to retrieve an article etc.; this option mayinclude the provision of an emergency release of the lock 114, in caseof some failure or breakdown that prevents a receiver from completingthe required actions;

(vii) the receiver will then approach the UAV 102, open a compartmentfor the article, e.g. by releasing a latch, or otherwise detach thearticle from the UAV 102, and where necessary close a compartment;

(viii) the receiver may then send a signal, e.g. by reentering theaccess code, or entering a different code provided, to the control panel116 which will communicate with the flight management system 150, toindicate that the article has been retrieved;

(ix) the flight management system 150 will then check that the articlehas been retrieved, by confirming that the measured weight of the UAV,as measured by the UAV pad 200, has been reduced by the weight of thearticle, and will also confirm that any required actions such asrelatching or closing a compartment have been completed;

(x) once the flight management system 150 has confirmed these actions,i.e. retrieval of the article and closure of a compartment on the UAV,the lock 114 is then again released;

(xi) the receiver can then reenter the local destination access code, toopen the lock 114, so the receiver may exit the departure location 100bearing the article; when the receiver closes the closure or gate 112,the lock 114 secures the closure 112; at this time, the receiver'sdestination access code may then be rendered inoperative, to prevent anyreentry by the receiver into the location 100, and optionally, this mayonly be after the receiver has sent a communication to the flightmanagement system 150 confirming that receipt of the article is completeand/or after a predetermined period of time after the receiver hasexited the destination location.

Reference will now be made to FIGS. 2 and 3 which show alternativelocations that include, respectively, two and four individual andseparate zones. For simplicity and brevity, like components in FIGS. 2and 3 are given the same reference numeral as in FIG. 1, and it will beunderstood that in general the individual components of the locationshown in FIG. 1 will be duplicated for each of the zones shown in FIGS.2 and 3.

Thus, in FIG. 2, a location 300 has an enclosure 306 with a barrier 304,which includes an additional dividing wall 332. This provides for afirst zone 308 with an identifier 328 for landing and taking off, and asecond zone 326 with an identifier 330 for landing and taking off, eachof which can be accessed separately through a respective closure or gate112, to ensure that, for each zone, only authorized personnel are givenaccess.

Similarly in FIG. 3, a barrier 404 is divided by walls 440 into fourseparate zones 408, 426, 432 and 436, with respective identifiers 428,430, 434 and 438. Each zone is provided with its own access closure orgate 112. (It will be understood that in order to show details of eachzone, in FIGS. 1, 2 and 3, barrier and dividing walls are showncutaway.)

Reference will now be made to FIG. 5 which shows a further embodiment ofa controlled access UAV zone. As for other UAV zones locations, it willbe understood that the features of this zone can be provided singularly,or in a complex including a plurality of zones, with features differentbetween the zones as required.

Similarly to other embodiments, a location 500 has an enclosure 506, abarrier 504 around the enclosure, and a landing and takeoff zone 508. Asfor other embodiments, it will be understood that the enclosure 506 isshown cutaway. An opening 510 in the barrier 504 is closed by a door orother closure 512, secured by a remotely operable lock 514.

A control and communication unit 516 is provided, and shown in greaterdetail in FIG. 6. The control and communication unit 516 has aninterface that will provide for two-way communication with the user. Forthis purpose, it may include a monitor screen 518 for displayinginformation, a keypad 520 for a user to input data or information, aloudspeaker 522 communicating with the user and a camera 524 for viewinguser activities. The unit 516 may also include a credit card readerindicated schematically at 526 and a printer indicated at 528. Themonitor by 18 may be in the form of a touchscreen, so a separate keypad520 or other input device would not be required.

All or some of the functionality of the control and communication unit516 may be provided externally of the location 500, so as to provide fora security check before a user is permitted to enter location 500. Forexample, an interface provided outside the location 500, which may be akeypad, can require a user to enter a previously approved username andpassword, before the lock 514 is opened. Additionally, in known mannertwo factor authentication can be provided, where a password or code istransmitted to an electronic device or phone of the user, and the useris then required to enter that password or code into the externalinterface, before obtaining access to the location 500. Alternatively,as shown, the entire control and communication unit 516 can be providedinside of the location 500, and a user may communicate wirelessly, e.g.from a smart phone, with the unit 516, to gain access to the location500.

To enable charging of a UAV 102, charging cables 530 are provided, andas indicated include suitable connectors 532 for connection to a UAV102. Two charging cables 530 are shown, as UAVs commonly have separatebatteries, requiring separate charging, namely an avionics battery foravionics and control electronics, and a propulsion battery with a largercapacity, for supplying power required to propel the UAV. Thus, onecharging cable 530 is for charging the avionics battery and the othercharging cable 530 is for charging the propulsion battery. In the eventthat a UAV has a different number of batteries, then appropriatemodifications to the charging arrangement can be made, e.g. providingmore or fewer charging cables, each arranged to provide charge at arequired voltage and current, which may be different between thedifferent charging cables. Additionally, for use with a variety ofdifferent UAVs, the control and communication unit 516 can have aninput, for inputting identifying information for a UAV 102 requiringcharging, so that the voltage and current supplied to the chargingcables 530 can be adjusted to parameters suitable for that UAV. UAVzones including charging cable(s) can be considered to be chargingzones.

The cables 530 may be configured to require manual connection to theUAV. The cables and the connectors 532 may alternatively be configuredto provide automatic connection to a UAV provided it lands within aspecified area, so no human intervention is required.

A further aspect of the invention envisages providing one or both of adedicated UAV, indicated at 540, and medical supplies, particularlyemergency medical supplies, indicated schematically at 542. The UAV 540and medical supplies 542 are shown located at a separate location 500 a.As required, this may have the same functionality as the location 500,or alternatively it may be provided just with functions necessary forthe UAV 540. As shown, the location 500 a may not need any enclosure oraccess door. A location or zone provided with at least one of the UAV540 and medical supplies 542 can be considered to be a medical supplylocation.

The UAV 540 is stored and housed in the housing 544. Where the location500 is generally open and exposed, the housing 544 may be configured toprotect the UAV 540 from the elements, as it is envisaged that the UAV540 may be used only occasionally and will therefore be in storage forconsiderable periods of time. The housing 544 is provided with acommunications module 546, for communicating the status of the UAV 540,and in particular the status of the state of charge of batteries of theUAV 540 and/or the status of medical supplies 542 associated with theUAV. The communications module 546 may be equivalent to the controlpanel 116 described for other embodiments. For example, many medicalsupplies may have a limited life, and it may be desirable to ensure thatavailable supplies 542 have not expired before the art dispatched foruse.

UAVs are commonly only able to maneuver once they have lifted offvertically from a rest or storage position, the housing 544 may have atop or closure 548, in the form of a lid or roof, that may be openedremotely, to permit the UAV 540 to leave the housing 544, withoutrequiring manual intervention. The closure 548 is connected to thecommunications module 546, for operation thereof, and will serve toprotect the UAV. The closure 548 may be in the form of any of theembodiments shown in FIG. 7.

Similarly to the communication unit 516, charging cables 550 areprovided connected to the UAV 540, for maintaining avionics andpropulsion batteries in a charged state to enable remote operation,again without requiring manual intervention, connections to the chargingcables 550 should be such as to enable the UAV 540 to disconnect fromthe cables 550, by simply rising vertically.

When it is required to deploy the UAV 540 and its medical supplies 542,a signal can be sent via the communication module 546, to open theclosure 548. The UAV 540 is then provided with instructions to carry outa mission to deliver the medical supplies 542, and commences the missionby lifting off vertically out of the housing 544, disconnecting from thecables 550.

As indicated, the flight control system 150 is in communication withvarious components of the location 500 and the UAV 540. Communication isachieved through a network indicated schematically at 580. The controland communication unit 516, the communications module 546, the remotelyoperable lock 514 and the UAV 540 are all in communication with thenetwork 580, to receive commands from and to supply data to, asrequired, the flight management system 150. As detailed below, theflight management system may monitor remotely the status of batteries ofthe UAV 540 and/or medical supplies 542.

While the medical supplies 542 are shown attached to a dedicated UAV540, in an alternative embodiment medical supplies 542 can be storedseparately from the UAV. The medical supplies 542 may then be providedwith attachment fittings for attachment to a suitable UAV, or themedical supplies may be otherwise carried by a UAV. In this case, thehousing 544 would then be used solely to house the medical supplies 542.When it is required to deploy the supplies 542, the closure 548 would beopened, to permit a selected UAV to land and engage, or otherwise pickup the medical supplies 542. With the medical supplies 542 engaged, theUAV can then transport the supplies 542 to a desired location.

The status of the medical supplies 542 may be monitored in a variety ofways. The flight management system 150 may simply keep a record of themedical supplies 542 at different locations, with information on age,expiry dates and related information. However, this does leave themedical supplies 542 open to tampering or being exchanged for differentsupplies. Alternatively, the communications module 546 may be providedwith means for communicating with the medical supplies 542, at least togather basic information on age, expiry date etc. This purpose, themedical supplies 542 may be provided with barcodes or the like, whichare presented so as to be readable by the communications module 546.Alternatively, medical supplies 542 may be provided with electroniccommunication with the communications module 546.

Other parameters that may affect the status of the medical supplies 542may be monitored by the housing 544 and the communications module 546.For example, temperature and humidity parameters may be recorded, assome medical supplies may be adversely when subject to extremes of heatand humidity and data on temperature and humidity may be communicated tothe flight control system 150.

Additionally, where a UAV 540 is maintained and stored for a period oftime, specifically to deliver medical supplies, the state of charge ofthe batteries of the UAV can be monitored remotely by the flightmanagement system 150, so that when a request is made to deploy the UAV540, the flight management system can first check and confirm that it ischarged and ready for deployment.

It is envisaged that a plurality of the locations 100, 300, 500 will beprovided, located so as to provide convenient access to users, andspaced to meet the needs of users and to correspond with thecapabilities of UAVs. it may only be necessary to provide for medicalsupplies 542 and a UAV 540 to be stored and made available at selectedones of the locations, chosen to provide adequate coverage andavailability for the medical supplies within a defined geographic area,i.e. to ensure that anywhere within that geographic area is within theflying range of a UAV transporting the medical supplies. Further, forthe medical supplies 542, they could be located at specializedlocations, such as at a hospital, medical facility or doctor's offices.Such a specialized location may be provided only for the delivery ofmedical supplies, and not for general-purpose use as a location for UAVsto transport any type of article. Such a specialized location may beused for other medical related functions, e.g. receipt and delivery ofnon-emergency medical supplies to a hospital or medical facility.Locating the medical supplies at a specialized facility should alsofacilitate monitoring the medical supplies, ensuring that they have notexpired and replacing them as necessary.

It is anticipated that, for conventional (i.e. not emergency medical)articles, a UAV will deliver such articles between two of the locations100, 300, 500. For emergency medical supplies 542, delivery may beeffected to another of the locations 100, 300, 500. In particular, itmay be that the emergency medical supplies will be required at alocation associated with a hospital, medical facility or the like. Onthe other hand, often it is expected that the emergency medical supplieswill be required and will be delivered to the scene of an accident,remote for any location for UAV as described.

While the various locations 100, 300, 500 above have been described,generally, as being open at the top, to enable UAVs to land and takeoff,for many purposes and applications it may be desirable to provideenclosed locations, which will serve to protect UAVs and goods orpackages transported by UAVs from the weather and surroundingenvironment. For this purpose, FIG. 7 shows a number of alternativearrangements or embodiments for providing a fully enclosed location, anyone of which can be applied to locations described above, and also to adedicated UAV 540 provided with medical supplies 542.

FIG. 7 shows three separate locations indicated at 600 a, 600 b and 600c. For each of these locations 600 a, 600 b, 600 c, the featuresdescribed above for other locations may be incorporated. For example, asshown for the location 600 a, a barrier 604 a serves to define anenclosure 606 a. A door, gate or other closure 612 a provides for accessto the enclosure 606 a and may be secured with a lock 614 a. While notshown, the other locations 600 b and 600 c can be similarly equipped.

The location 600 a is provided with a covering or roof 620 in the formof a sliding or rolling tarpaulin system. A plurality of crossmembers622 extend across and between sidewalls 630. In known manner, thecrossmembers 622 are provided with rollers or other mechanisms forsliding movement along the tops of the sidewalls 630. Again, in knownmanner, cable or other drive systems can be provided along the top edgesof the sidewalls 634, for moving the crossmembers 622. The crossmembers622 are covered and connected by a tarpaulin or membrane generallyindicated at 624. The drive mechanism is provided for moving thecrossmembers 622 between an open and close configuration. As shown, thecovering 620 is in a partially open position, where crossmembers 622 atthe top of FIG. 7 are spaced apart with the tarpaulin 624 covering thelocation. Three crossmembers 622, as indicated at 622 a are bunchedclose together, as occurs when the roof 620 is being open or closed.

In the middle of FIG. 7, the location 600 b is in the form of aconventional pitched roof, comprising two roofing panels 640, which meetat the top to form a ridge. As indicated by an arrow 642 for one of thepanels 640, this can be pivoted upwards to the vertical position, andthe other panel 640 can simply be moved to a vertical position, tocompletely open the location 600 b, to enable UAVs to land and totakeoff.

On the right-hand side of FIG. 7, the location 600 c shows a furtheralternative, which recognizes that UAVs can travel horizontally.Provided the location has sufficient headroom, then a UAV can enter andleave the location in a horizontal direction. For this purpose, thelocation 600 c simply has a pair of doors 650, which in known manner canbe opened to provide full access to the interior of the location 600 c.As indicated by the arrow 652 for one of the doors 650, this would moveoutwardly to a position indicated at 650 a, and the other door wouldopen in a similar manner. Alternatively, the doors may open inwardly.

The medical supplies may be in accordance with those disclosed inapplicant's co-pending U.S. application Ser. Nos. 15/796,210 and15/796,252, both filed Oct. 27, 2017. Full contents of both thoseapplications are incorporated by reference

A controlled access UAV zone or location as disclosed can be provided ata variety of different places. For example, a drone delivery serviceoperator may provide a UAV parking zone or location at customers'premise, for each customer who regularly uses the drone deliveryservice. The customers could be, for example, manufacturers, shippers,distributors or other businesses. The controlled access UAV zone orlocation may also be provided at any suitable public location orbuilding. E.g., in smaller communities, it could be provided at aschool, hospital, town hall, public library, court house, shopping mall,etc., and may be a building or facility that is government owned andoperated or one that is privately owned and operated, such as a shoppingmall. A controlled access UAV location may also be provided at amulti-tenanted building, such as a condominium. For any building,including mid to high rise multi-occupant buildings, it may bepreferable to place the UAV location on the roof or other high point ofthe building.

In another aspect, a UAV parking zone or location could be provided foruse by several customers of drone delivery service. For example, acommon UAV parking zone or location can be provided at an industrialmall, where there are a number of businesses. In such a case, eachbusiness may be provided with an access code.

In some embodiments and depending on the UAV parking zone or locationand the businesses, a common access code for accessing the UAV parkingzone or location may be provided to the businesses. In otherembodiments, each business may be provided with a dedicated access code.Dedicated access codes may provide for, for example, tracking access tothe UAV parking zone or location, and setting up varying permissionlevels. The permission levels may include, for example, for eachdedicated access code one or more time slots during which the accesscode may provide access to a given UAV parking zone or location. Eachindividual access code may be made active, only when a UAV is arrivingor leaving with a delivery for that business.

In yet another aspect, a pay structure may be assigned to dedicatedaccess codes. Alternatively or as well, the pay structure could varydepending on time, e.g. time slots outside of regular business hourscould be less expensive than time slots in regular business hours. Insome examples, one or more permission levels may be assigned to a givendedicated access code depending on the terms of an agreement under whichthe code may be licensed or leased to a customer. In a particularexample, a customer access system may be provided using at least onecomputing system. The access system may be operable to provide a paystructure for dedicated access codes. For example, a year may be brokendown into weeks, days, and possibly hours.

The resulting time slots, days, and weeks may each be associated, eitherindividually or in groups, with varying levels of demand for a dronedelivery service at a given UAV parking zone or location. Accordingly,the system may be operable to sell, lease, or rent out dedicated accesscodes depending on the access or permission level(s) requested by acustomer for each of the access codes.

For example, the customer access system may be operable to assign to agiven dedicated access code, permissions for that code to provide accessto a given UAV parking zone or location on certain days, e.g. Mondays,Wednesdays, and Fridays, and may be operable to assign a given sale,lease, or rent rate or value (for example, expressed in dollars) to thatcode, or type of code. The system may be further operable to assigndifferent permissions and lease, or rent rate or value to differentdedicated access codes or types or classes of dedicated access codes.

In a further aspect, the customer access system may be operable toassign different limits for at least one of UAV landings and take-offs,and corresponding pricing, for different dedicated access codes,dedicated access code types, or dedicated access code classes. Forexample, the customer access system may be operable to sell dedicatedaccess codes on at least one of a per-UAV-landing and a per-UAV-take-offbasis. That is, the system may assign a given price for each UAV landingand each UAV take-off, the pricing may vary depending on time, locationand other factors, and may also provide discounts where, for example, aminimum number or numbers of landings and take-offs are purchased by acustomer.

In yet a further aspect, the system may assign a dedicated access codeto a given customer, and may be operable to request “re-fills” oflandings and take-offs when the customer uses all pre-purchased landingsand take-offs at the UAV parking zone or location to which that code maybe assigned. In another aspect, the system may be operable to track thenumber of landings and take-offs used by each customer and may beoperable to bill each customer based on the number and based on, forexample, a payment method chosen by each customer. In one example, acustomer may provide at least one of a credit card and a debit card andauthorization to charge the card(s) on, for example, a weekly or amonthly basis.

Other aspects are described next. In one aspect, if one of thebusinesses at the example industrial mall, a customer of the dronedelivery service, is either sending an article or expecting delivery ofan article by the drone delivery service, only that customer's accesscode may permit access to the UAV zone or location while this deliveryoperation is taking place.

For a package to be sent from the UAV zone or location, access to thelocation may be restricted to that customer, until the UAV has picked upthe article and departed from the UAV zone or location. At that time,the UAV zone or location may be released for use by another customer.Similarly, while the UAV is delivering an article to one customer,access may be restricted to that one customer, until at least thecustomer has accessed the UAV zone or location and retrieved thedelivered article.

A UAV zone or location as disclosed can be provided in a variety ofdifferent places. It can be provided simply on any suitable flat,unobstructed piece of ground. Alternatively, and for an example in amore crowded or industrial setting, the UAV zone or location may beprovided on top of a building with a flat roof, or a building on which alarge enough flat landing and take-off area can be constructed. Anadvantage of providing a UAV zone or location on top of a building maybe that it may reduce the requirement for a UAV to fly down betweenobstructions such as poles, power cables, other buildings, and the likeand may reduce the possibility for accidents. A rooftop location alsoinherently limits access, and it may not be necessary to provide abarrier around such a location for security purposes; a barrier maystill be desirable for safety purposes, e.g., around the edge of a flatrooftop.

In addition to locations identified above, a UAV location as disclosedcan be provided at warehouses, distribution centers, cross-dockingfacilities, order fulfillment facilities, packaging facilities, shippingfacilities, rental facilities, libraries, retail stores, wholesalestores, museums, or other facilities or combinations thereof.

In a variant embodiment, a simplified UAV zone or location may beprovided. This may be suitable for a location that receives low trafficvolumes and/or may be temporary, so that the cost of the fully equippedzone or location is not justified.

A simplified UAV zone may include just some form of an enclosure orbarrier to control access to the zone. As for other zones locations, itmay include an access door or gate, with a lock, and the lock may becontrolled remotely by a flight management system. The zone or locationcould be provided anywhere, and the interior or base may be leftunfinished, i.e. it would not be finished or equipped for the landing ofa UAV.

Then, to enable a package to be delivered, the following sequence may beeffected:

-   -   (a) the zone or location will be secured, and a flight        management system may check to ensure that an access to the zone        is closed and locked;    -   (b) to deliver a package to the zone or location, a UAV would        travel to the zone;    -   (c) on arriving at the zone, the UAV would simply hover over the        zone or location, and then drop the package from a predetermined        height, e.g. 5, 10, 15, 20 or 25 feet;    -   (d) once the package has been dropped, the UAV can depart,        without having to land at the zone or location, and may        optionally transmit a signal to indicate that the package has        been delivered and dropped;    -   (e) on receipt of the signal from the UAV, the flight management        system can then release the lock on the door or gate, to enable        access to the zone or location by ground personnel, to retrieve        the package;    -   (f) optionally, instead of or as well as relying on a signal        from the UAV, the zone or location can be provided with sensors        to detect that a package has been dropped into the zone or        location, to enable the lock to be opened and a notification of        the package delivery to be sent to an intended recipient, for        the recipient to pick up the package; and    -   (g) also optionally, the zone or location may be provided with        various devices to cushion a dropped package, for example a net        could be strung up within the zone or location, or foam padding        or the like may be provided.

To enable a UAV to navigate accurately to such a simplified zone orlocation, a homing beacon may be provided at the zone or location, sothat the UAV, at the end of its flight route, can simply home in on thebeacon. It may also be possible to use an electronic device carried by auser. For example, at a temporary or other location, a user may firstaccess the location and then leave a smart phone or other electronicdevice that transmits positional information, in the location. The userthen exits the location, secures unlocks the location, as checked andconfirmed by a flight management system, so that the UAV may deliver apackage. The UAV then homes in on the smart phone or other electronicdevice, to ensure that the package is delivered at the correct location.

It will be understood that such a simplified UAV zone or location isintended primarily for delivery of the package, without the UAV landing.It may be possible for a UAV to pick up a package, if the package isprovided with some form of a tether or hook that the UAV can engage,without the UAV landing.

While the UAV shown is a multirotor helicopter, a UAV location can beconfigured for any type of UAV, including multirotor helicopters, suchas a quadcopter or a fixed wing craft. For example, the UAV may includea combination of both propellers and fixed wings. For example, the UAVmay utilize one or more propellers to enable take-off and landing and afixed wing configuration or a combination wing and propellerconfiguration to sustain flight while the UAV is airborne. A UAVlocation for UAVs not adapted for vertical landing and take-off will beconfigured to provide suitable flight paths for landing and take-off.

A UAV for use with the UAV location disclosed can include anyinstrumentation suitable for assisting in the control of the UAV,including a time of flight sensor or calculator, radar, sonar, a camera,an infrared sensor, one or more displays, image capture devices, thermalsensors, accelerometers, pressure sensors, weather sensors, LIDAR,sensors for detecting hazardous materials, etc.

Further, while the invention has been described for use with aerialvehicles, it may be applied to land vehicles, such as robots orautonomously guided vehicles as cars, the travel along road systems.

The apparatuses, systems, functions, and methods described in thisdocument may be implemented using any combination of suitable knowntechnology, materials, and manufacturing, assembly, and programmingmethods.

A number of embodiments have been described herein. However, it will beunderstood by persons skilled in the art that other variants andmodifications may be made without departing from the scope of theembodiments as defined in the claims appended hereto. A person skilledin the art will also recognize that the embodiments described aboveshould be read as representative of a plethora of permutations notexplicitly described, the permutations incorporating elements fromvarious embodiments.

1. A UAV location management method for use with a flight managementsystem, the method comprising: providing a location for at least oneunmanned aerial vehicle (UAV) for at least one of: landing, taking-offand loading; providing at least a first weight-sensitive UAV pad at theUAV location; assigning a gross weight limit to each UAV scheduled totake-off from the first weight-sensitive UAV pad, the gross weight limitbeing based on a safety factor and at least one of: (i) a characteristicof the UAV; (ii) a characteristic of a power source of the UAV; (iii) ascheduled flight path for the UAV; and (iv) a weather condition;monitoring a weight exerted on the first weight-sensitive UAV pad whenthe UAV is positioned on the UAV pad; and transmitting a halt-flightsignal to the flight management system for the UAV where the weightexceeds the gross weight limit.
 2. The method of claim 1, furthercomprising: after receiving a request for delivery of an article,generating a departure access code for the location; once the UAV ispresent at the location, checking with the flight management systemavailable sensors for unauthorized movement or presence of unauthorizedobjects; once it is confirmed that there are no obstructions at thelocation, transmitting to the control panel a signal to open a lock, topermit access to the location; on receipt of the departure access code,opening the lock, to permit a receiver to enter the location, where thereceiver secures an article to the UAV as a payload for delivery andthen exits the location; and if the weight of the UAV does not exceedthe gross weight limit, causing the UAV to take-off to deliver thearticle secured to the UAV to a destination location.
 3. The method ofclaim 1, further comprising receiving a delivery by a UAV at thelocation, the method comprising: permitting the UAV to land at thelocation, once it is confirmed that a closure for that location isclosed and locked and that there are no obstructions present; after theUAV has landed at the location, sending a signal to the lock, so as topermit the lock to be opened by a destination access code provided atleast to each receiver that has been identified to a control panel atthe location; with the destination access code entered, opening thelock, so the receiver may open the closure, to gain access to thelocation and retrieve the article from the UAV; and checking that thearticle has been retrieved, by confirming that the measured weight ofthe UAV at the UAV pad has been reduced by the weight of the article. 4.The method of claim 3, further comprising: causing the UAV to depart thelocation with another article; and prior to the departure, having theflight management system run pre-flights checks on the UAV, the checkscomprising: checking the weight of the UAV with the other article andcomparing it to the gross weight limit; checking on the availablebattery life for the UAV; and checking on weather condition along aflight path for the UAV.
 5. The method of claim 1, further comprising:providing a first UAV-readable identifier at the first UAV pad, whereinthe identifier identifies at least one of: the location of the UAV padand an identity of the UAV pad; providing at least a second UAV pad forat least UAV take-offs; and providing a second UAV-readable identifierfor the second UAV pad, the second UAV-readable identifier beingdistinguishable by a UAV from the first UAV-readable identifier.
 6. Themethod as claimed in claim 1, further comprising: providing a cleanerfor the location; monitoring for at least one obstruction to thelocation; determining the at least one obstruction as being one of atleast one animate object, at least one inanimate object, and at leastone animate object in combination with at least one inanimate object;and when the obstruction is determined to be at least one inanimateobject, performing at least one of: restricting access to the UAVlocation; transmitting an instruction to the flight management system tohalt UAV flights and take-offs to and from the UAV location; andtransmitting an instruction to the cleaner to clear the obstruction fromthe UAV location.
 7. An unmanned aerial vehicle (UAV) system,comprising: a plurality of controlled access UAV zones, each being forat least one of: UAV landing, UAV loading, and UAV take-off, that isaccessible by a UAV; for each zone, a control panel at the controlledaccess UAV zone; a flight management system separate from the pluralityof zones and in communication with the control panels thereof; for eachzone, at least a first weight-sensitive UAV pad for determining a grossweight of the UAV when position on the UAV pad; and at least onecomputing system configured to: assign a gross weight limit to each UAVscheduled to take-off from the first weight-sensitive UAV pad, the grossweight limit being based on a safety factor and at least one of: acharacteristic of the UAV; a characteristic of a power source of theUAV; a scheduled flight path for the UAV; and a weather condition; andtransmit a halt-flight signal to the flight management system for theUAV where the gross weight exceeds the gross weight limit.
 8. The UAVsystem of claim 7, further comprising the at least one computing systembeing configured to: after receiving a request for delivery of anarticle, generate a departure access code for each UAV zone; once theUAV is present at a UAV zone, check with the flight management systemavailable sensors for unauthorized movement or presence of unauthorizedobjects at the UAV zone; once it is confirmed that there are noobstructions at the location, transmit to the corresponding controlpanel a signal to open a lock, to permit access to the UAV zone, wherethe corresponding control panel is configured to, on receipt of thedeparture access code, open the lock to permit a receiver to enter theUAV zone to secure an article to the UAV as a payload for delivery; andif the weight of the UAV does not exceed the gross weight limit, causethe UAV to take-off to deliver the article secured to the UAV to adestination location.
 9. The UAV system of claim 6, further comprisingthe at least one computing system being configured to: permit the UAV toland at a UAV zone, once it is confirmed that a closure for that UAVzone is closed and locked and that there are no obstructions present;after the UAV has landed at the UAV zone, transmit a signal to the lock,so as to permit the lock to be opened by a destination access codeprovided at least to each receiver that has been identified to thecontrol panel at the UAV zone, such that the control panel is configuredto open the lock, with the destination access code entered, so thereceiver may open the closure to gain access to the UAV zone andretrieve the article from the UAV; and check that the article has beenretrieved, by confirming that the measured weight of the UAV at the UAVpad has been reduced by the weight of the article.
 10. The UAV system ofclaim 9, further comprising the at least one computing system beingconfigured to cause the UAV to depart the location with the otherarticle and, prior to the departure, the flight management system beingconfigured to run pre-flights checks on the UAV, the checks comprising:checking the weight of the UAV with another article and comparing it tothe gross weight limit; checking on the available battery life for theUAV; and checking on weather condition along a flight path for the UAV.11. The UAV system of claim 6, further comprising: the first UAV padcomprising a first UAV-readable identifier, wherein the identifieridentifies at least one of: the location of the UAV pad and an identityof the UAV pad; a second UAV pad for at least UAV take-offs; and thesecond UAV pad comprising a second UAV-readable identifier, the secondUAV-readable identifier being distinguishable by a UAV from the firstUAV-readable identifier.
 12. The UAV system as claimed in claim 6,further comprising: a cleaner at each UAV zone; and for each UAV zone,the at least one computing system being configured to monitor for atleast one obstruction at the UAV zone; determine the at least oneobstruction as being one of at least one animate object, at least oneinanimate object, and at least one animate object in combination with atleast one inanimate object; and when the obstruction is determined to beat least one inanimate object, perform at least one of: restrictingaccess to the UAV zone; transmitting an instruction to the flightmanagement system to halt UAV flights and take-offs to and from the UAVzone; and transmitting an instruction to the cleaner to clear theobstruction from the UAV zone.